Open
Conversation
Contributor
|
Can you make it so that once a request is sent out other request are not sent out as well until after we get a response back from the first request. For example if we send try and get(A), and while we are getting that another call to get(A) comes, we don't want to re-do the request. Could you either add a wait flag or change how caching is done such as with a on fail callback, which will call the callback code. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Caching function currently used for getUserTeam and getUserProfile. I'm not too sure about how the scrimmage functions are going to be used so I've not cached those functions yet. Currently, the default timeout is set to be 30 minutes.